Credential entry and management

ABSTRACT

The present embodiments relate to entry and management of identifiers and credentials. The present embodiments display a credential affordance that, upon selection, provides a credential-assistance user interface for enabling swift access to various credential and management options. The credential affordance can be displayed based on a determination by electronic device that a webpage includes a text entry field associated with a set of one or more restricted resources (e.g., document and/or webpage).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/111,042, entitled “CREDENTIAL ENTRY AND MANAGEMENT,” filed Aug. 23,2018, which is a continuation of U.S. patent application Ser. No.14/869,974, entitled “CREDENTIAL ENTRY AND MANAGEMENT,” filed Sep. 29,2015, which claims priority to U.S. Provisional Patent Application No.62/172,220, entitled “CREDENTIAL ENTRY AND MANAGEMENT,” filed Jun. 7,2015, the content of each of which is hereby incorporated by referencein its entirety for all purposes.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for credential entry and management.

BACKGROUND

Electronic devices may present a credential entry interface in a webbrowser for secure access to one or more webpages. For example, a usermay navigate, in the web browser, to a webpage for accessing securecontent. The webpage may request a verification of the user's identityprior to providing access to the secure content. However, electronicdevices may be limited in providing a way for entry and management ofidentifiers and/or credentials, for example, in a web browser.

BRIEF SUMMARY

Some techniques for entry and management of credentials using electronicdevices, however, are generally cumbersome and inefficient. Forinstance, webpages may not always be provided in markup language thatunequivocally identifies a credential-based field that would facilitateautofill. Further, for example, existing techniques may use a complexand time-consuming user interface, which may include multiple contactinputs, key presses or keystrokes. Existing techniques require more timethan necessary, detracting from the user's experience, and wasting usertime and device energy. This latter consideration may be particularlyimportant in battery-operated devices.

Accordingly, the present embodiments provide for electronic devices withfaster, more efficient methods and interfaces for entry and managementof credentials. Such methods and interfaces optionally complement orreplace other methods for entry and management of credentials. Suchmethods and interfaces reduce the cognitive burden on a user and producea more efficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

The present embodiments provide for methods and/or interfaces that alsoreduce the number of unnecessary, extraneous, repetitive, and/orredundant inputs, and may create a faster and more efficient userinterface arrangement, which may reduce the number of required inputs,reduce processing power, and reduce the amount of time for which userinterfaces need to be displayed in order for desired functions to beaccessed and carried out

In accordance with some embodiments, a method is performed at anelectronic device including a display and memory: displaying, on thedisplay, a text entry field associated with a set of one or morerestricted resources and a credential affordance associated with thetext entry field; receiving a first input corresponding to selection ofthe credential affordance; in response to receiving the first input,displaying a credential-assistance user interface, wherein displayingthe credential-assistance user interface includes: in accordance with adetermination that a credential is stored in the memory, displaying anidentifier associated with the credential in the credential-assistanceuser interface; and receiving an input corresponding to selection of theidentifier; and in response to receiving the input corresponding toselection of the identifier, retrieving the credential stored in thememory and entering the credential into the text entry field.

In accordance with some embodiments, a non-transitory computer-readablestorage medium comprises one or more programs for execution by one ormore processors of an electronic device, the one or more programsincluding instructions which, when executed by the one or moreprocessors, cause the electronic device to: display a text entry fieldassociated with a set of one or more restricted resources and acredential affordance associated with the text entry field; receive afirst input corresponding to selection of the credential affordance; inresponse to receiving the first input, display a credential-assistanceuser interface, wherein displaying the credential-assistance userinterface includes: in accordance with a determination that a credentialis stored in a memory, display an identifier associated with thecredential in the credential-assistance user interface; and receive aninput corresponding to selection of the identifier; and in response toreceiving the input corresponding to selection of the identifier,retrieve the credential stored in the memory and entering the credentialinto the text entry field.

In accordance with some embodiments, an electronic device comprises: oneor more processors; memory; a display to the one or more processors andmemory; and one or more programs stored in memory, the one or moreprograms including instructions for: displaying, on the display, a textentry field associated with a set of one or more restricted resourcesand a credential affordance associated with the text entry field;receiving a first input corresponding to selection of the credentialaffordance; in response to receiving the first input, displaying acredential-assistance user interface, wherein displaying thecredential-assistance user interface includes: in accordance with adetermination that a credential is stored in the memory, displaying anidentifier associated with the credential in the credential-assistanceuser interface; and receiving an input corresponding to selection of theidentifier; and in response to receiving the input corresponding toselection of the identifier, retrieving the credential stored in thememory and entering the credential into the text entry field.

In accordance with some embodiments, a method is performed at anelectronic device including a display and memory: receiving a request todisplay a document that includes a text entry field; in response toreceiving the request, displaying the document with the text entryfield, wherein displaying the document with the text entry fieldincludes: in accordance with a determination that the text entry fieldcorresponds to a credential entry field for which a stored credential isavailable, filling in the text entry field with the stored credential;and in accordance with a determination that the text entry fieldcorresponds to a credential entry field for which a stored credential isnot available, displaying, on the display, a credential affordanceassociated with the text entry field without filling in the text entryfield. Further, the method may be implemented as part of or within asystem, apparatus, and/or computer-readable medium.

In accordance with some embodiments, a non-transitory computer-readablestorage medium comprises one or more programs for execution by one ormore processors of an electronic device, the one or more programsincluding instructions which, when executed by the one or moreprocessors, cause the electronic device to: receive a request to displaya document that includes a text entry field; in response to receivingthe request, display the document with the text entry field, whereindisplaying the document with the text entry field includes: inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is available,fill in the text entry field with the stored credential; and inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is not available,display a credential affordance associated with the text entry fieldwithout filling in the text entry field.

In accordance with some embodiments, an electronic device comprising:one or more processors; memory; a display to the one or more processorsand memory; and one or more programs stored in memory, the one or moreprograms including instructions for: receiving a request to display adocument that includes a text entry field; in response to receiving therequest, displaying the document with the text entry field, whereindisplaying the document with the text entry field includes: inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is available,filling in the text entry field with the stored credential; and inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is not available,displaying, on the display, a credential affordance associated with thetext entry field without filling in the text entry field.

Thus, devices are provided with faster, more efficient methods andinterfaces for credential entry and management (e.g., in a web browser),thereby increasing the effectiveness, efficiency, and user satisfactionwith such devices. Such methods and interfaces may complement or replaceother methods for entry of credentials.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6A illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6B illustrates another example user interface for credential entryand management in accordance with some embodiments.

FIG. 6C illustrates a further example user interface for credentialentry and management in accordance with some embodiments.

FIG. 6D illustrates an additional example user interface for credentialentry and management in accordance with some embodiments.

FIG. 6E illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6F illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6G illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6H illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6I illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6J illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6K illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6L illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6M illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6N illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6O illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 6P illustrates an example user interface for credential entry andmanagement in accordance with some embodiments.

FIG. 7A is a flow diagram of an example process of credential entry andmanagement in accordance with some embodiments.

FIG. 7B is a flow diagram of a further example process of credentialentry and management in accordance with some embodiments.

FIG. 8 is a functional block diagram in accordance with someembodiments.

FIG. 9 is a functional block diagram in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

The present embodiments generally relate to entry and management ofidentifiers and credentials. For example, an electronic device such as amobile device enables a user to navigate to a webpage within a browserinterface of a browser application. In some embodiments, the webpagedisplays a credential entry interface in the browser interface forsecure access to secure content within the webpages. That is, thewebpage presents the credential entry interface to verify the identityof the user prior to providing access to the secure content.

In some embodiments, upon navigation to a webpage having a credentialentry interface for verifying a user's identity and/or permitting accessto secure content, the browser interface automatically enterspreviously-entered and stored identifier and/or credential informationin corresponding text entry fields. The foregoing may be referred to asautomatically filling in of text entry fields (e.g., “autofill”).However, in some embodiments, the browser interface may not determine,to a degree of certainty, that the webpage includes an identifier and/orcredential entry access procedure. In other words, the browser interfacemay not have detected the login procedure, and hence, did not autofillone or more corresponding text entry fields (e.g., username and/orpassword fields).

As such, the present embodiments provide enhanced entry and managementof credentials. For example, the present embodiments display acredential affordance that, upon selection, provides acredential-assistance user interface for enabling swift access tovarious credential and management options. In some embodiments, thecredential affordance is displayed based on a determination byelectronic device that a webpage includes a text entry field associatedwith a set of one or more restricted resources (e.g., secure documentand/or webpage). That is, upon navigating to a webpage, the electronicdevice displays, in the browser interface, the credential affordancewhen an autofill failure is detected and/or secure access resources(e.g., username and/or password fields) are detected.

Accordingly, there is a need for electronic devices that provideefficient methods and interfaces for entry and management of identifierand/or credentials, for example, browser interface. Such techniques canreduce the cognitive and/or physical burden on a user in entering andmanaging credentials in a browser interface, thereby enhancingefficiency and productivity. Further, such techniques can reduceprocessor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for movement betweenmultiple views. FIGS. 6A-6P illustrate exemplary user interfaces forentry and management of credentials. The user interfaces in the figuresare also used to illustrate the processes described below, including theprocess in FIGS. 7A & 7B.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” can optionally be construed to mean “when” or “upon” or“in response to determining” or “in response to detecting,” depending onthe context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” can optionally be construed tomean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device can optionally support a variety of applications, such as oneor more of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 can optionally include one or more computer-readable storagemediums. The computer-readable storage mediums can optionally betangible and non-transitory. Memory 102 can optionally includehigh-speed random access memory and can optionally also includenon-volatile memory, such as one or more magnetic disk storage devices,flash memory devices, or other non-volatile solid-state memory devices.Memory controller 122 can optionally control access to memory 102 byother components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 can optionally beimplemented on a single chip, such as chip 104. In some embodiments,they can optionally be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data can optionally beretrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output can optionallyinclude graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output can optionally correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 can optionally use LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiescan optionally be used in some embodiments. Touch screen 112 and displaycontroller 156 can optionally detect contact and any movement orbreaking thereof using any of a plurality of touch sensing technologiesnow known or later developed, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with touch screen 112. In an exemplaryembodiment, projected mutual capacitance sensing technology is used,such as that found in the iPhone® and iPod Touch® from Apple Inc. ofCupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 canoptionally be analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 canoptionally be as described in the following applications: (1) U.S.patent application Ser. No. 11/381,313, “Multipoint Touch SurfaceController,” filed May 2, 2006; (2) U.S. patent application Ser. No.10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patentapplication Ser. No. 10/903,964, “Gestures For Touch Sensitive InputDevices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No.11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31,2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-BasedGraphical User Interfaces For Touch Sensitive Input Devices,” filed Jan.18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “VirtualInput Device Placement On A Touch Screen User Interface,” filed Sep. 16,2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of AComputer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S.patent application Ser. No. 11/228,737, “Activating Virtual Keys Of ATouch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patentapplication Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,”filed Mar. 3, 2006. All of these applications are incorporated byreference herein in their entirety.

Touch screen 112 can optionally have a video resolution in excess of 100dpi. In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user can optionally make contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100 canoptionally include a touchpad (not shown) for activating or deactivatingparticular functions. In some embodiments, the touchpad is atouch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad can optionally be atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 can optionally include a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 can optionally also include one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 can optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 can optionallycapture still images or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch screen display 112 onthe front of the device so that the touch screen display can optionallybe used as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image can optionally be obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 can optionally be used along with the touch screendisplay for both video conferencing and still and/or video imageacquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 can optionally also include one or more proximity sensors166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface118. Alternately, proximity sensor 166 can optionally be coupled toinput controller 160 in I/O subsystem 106. Proximity sensor 166 canoptionally perform as described in U.S. patent application Ser. No.11/241,839, “Proximity Detector In Handheld Device”; Ser. No.11/240,788, “Proximity Detector In Handheld Device”; Ser. No.11/620,702, “Using Ambient Light Sensor To Augment Proximity SensorOutput”; Ser. No. 11/586,862, “Automated Response To And Sensing Of UserActivity In Portable Devices”; and Ser. No. 11/638,251, “Methods AndSystems For Automatic Configuration Of Peripherals,” which are herebyincorporated by reference in their entirety. In some embodiments, theproximity sensor turns off and disables touch screen 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 can optionally also include one or more accelerometers 168.FIG. 1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 can optionally be coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 can optionallyperform as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which can optionally be a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 can optionally include the following modules (or setsof instructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which can optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that can optionally be stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 can optionally be used to manage an addressbook or contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 can optionally be used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication can optionally use any of a pluralityof communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages can optionally include graphics, photos, audio files,video files and/or other attachments as are supported in an MMS and/oran Enhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that can optionally be downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150can optionally be used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154can optionally be used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). Executable instructions for performing thesefunctions are, optionally, included in a non-transitorycomputer-readable storage medium or other computer program productconfigured for execution by one or more processors. These modules (e.g.,sets of instructions) need not be implemented as separate softwareprograms, procedures, or modules, and thus various subsets of thesemodules can optionally be combined or otherwise rearranged in variousembodiments. For example, video player module can optionally be combinedwith music player module into a single module (e.g., video and musicplayer module 152, FIG. 1A). In some embodiments, memory 102 canoptionally store a subset of the modules and data structures identifiedabove. Furthermore, memory 102 can optionally store additional modulesand data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some embodiments, the menubutton is a physical push button or other physical input control deviceinstead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In some embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected can optionally be calledthe hit view, and the set of events that are recognized as proper inputscan optionally be determined based, at least in part, on the hit view ofthe initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In some embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In some embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In someembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In some embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 can optionally utilize or call dataupdater 176, object updater 177, or GUI updater 178 to update theapplication internal state 192. Alternatively, one or more of theapplication views 191 include one or more respective event handlers 190.Also, in some embodiments, one or more of data updater 176, objectupdater 177, and GUI updater 178 are included in a respectiveapplication view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which can optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation can optionally also include speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In some embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 can optionally also include one or more physical buttons,such as “home” or menu button 204. As described previously, menu button204 can optionally be used to navigate to any application 136 in a setof applications that can optionally be executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 can optionally be storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules can optionally be combined or otherwiserearranged in various embodiments. In some embodiments, memory 370 canoptionally store a subset of the modules and data structures identifiedabove. Furthermore, memory 370 can optionally store additional modulesand data structures not described above.

Attention is now directed towards embodiments of user interfaces thatcan optionally be implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces can optionally be implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 can optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) canoptionally have one or more intensity sensors for detecting intensity ofcontacts (e.g., touches) being applied. The one or more intensitysensors of touch screen 504 (or the touch-sensitive surface) can provideoutput data that represents the intensity of touches. The user interfaceof device 500 can respond to touches based on their intensity, meaningthat touches of different intensities can invoke different userinterface operations on device 500.

Techniques for detecting and processing touch intensity are found, forexample, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 can optionally be a rotatable input device or adepressible and rotatable input device, for example. Input mechanism 508can optionally be a button, in some examples.

Input mechanism 508 can optionally be a microphone, in some examples.Personal electronic device 500 can include various sensors, such as GPSsensor 532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 702-712 (FIG. 7). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions. Forpurposes of this document, a “non-transitory computer-readable storagemedium” can be any medium that can tangibly contain or storecomputer-executable instructions for use by or in connection with theinstruction execution system, apparatus, or device. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that can be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) canoptionally each constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds canoptionally include a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation) rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location canoptionally be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmcan optionally be applied to the intensities of the swipe contact priorto determining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface can optionallybe characterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

FIGS. 6A-6P illustrate example user interfaces for credential entry andmanagement in accordance with some embodiments. For example, anelectronic device enables a user to navigate to an interface requiringcredentials in order to access restricted resources. In someembodiments, the device autofills the credentials in a text entry field.However, the user may wish to alter the content of the text entry field.

Accordingly, the present embodiments provide control over thecredentials entered in a text entry field. Specifically, a credentialaffordance associated with the text entry field is displayed. Inresponse to receiving input associated with the credential affordance, acredential-assistance user interface is displayed, allowing the user toselect a credential stored in memory.

The embodiments of FIGS. 6A-6P are implemented in an electronic deviceincluding a display and memory. In some embodiments, electronic deviceis the same as or similar to portable multifunction device 100 (FIG. 1),multifunction device 300 (FIG. 3), and/or personal electronic device 500(FIG. 5). Further, in some embodiments, display is the same as orsimilar to one touch-sensitive display system 112 (FIG. 1), display 340(FIG. 3), and/or touch-sensitive display screen 504 (FIG. 5). In someembodiments, the memory is the same as or similar to memory 102 (FIG.1A), memory 370 (FIG. 3), and/or memory 518 (FIG. 5B).

Referring to FIG. 6A, a browser interface 600 is illustrated inaccordance with some embodiments. Specifically, browser interface 600 isa browser of a browser application (e.g., Safari released by Apple Inc.of Cupertino, Calif.) for retrieving, presenting and traversinginformation resources (e.g., webpage content) on the World Wide Web.Browser interface 600 is displayed on a display such as display 112(FIG. 1), 340 (FIG. 3), and/or 504 (FIG. 5).

Browser interface 600 includes a set of control affordances 602 forenabling navigation and control of the interface. In a non-limitingexample, the one or more control affordances 602 include an exitaffordance, a previous webpage affordance, a forward webpage affordance,and address bar that includes a current resource locator (URL) andaccepts an entered URL that navigates the user to a chosen webpage inbrowser interface 600.

The electronic device configures browser interface 600 to display adocument and/or webpage 604 having a set of one or more restrictedresources. In some embodiments, the webpage is a login page foraccessing secure content. In particular, in order to provide or grantaccess to the secure content, the login page requests a user enter anidentifier and a credential. In some embodiments, the identifier is ausername and the credential is a password. In some embodiments, theidentifier is a domain of the webpage. In some embodiments, the set ofrestricted resources is a document and/or webpage.

Specifically, to enable access to secure content or otherwise allow auser to login or navigate to another (e.g., secured) webpage, electronicdevice configures browser interface 600 to display a text entry field608. In some embodiments, text entry field 608 is a credential field,which is also referred to as a password field. Further, browserinterface 600 also displays another text entry field in the form of anidentifier field 606, which is referred to as a username field, andaccepts entry of text associated with an identifier (e.g., username).

In some embodiments, electronic device configures browser interface 600to automatically fill one or both of the identifier field 606 and thetext entry field 608 (e.g., credential/password field). However, in someembodiments, the browser interface 600 does not determine that webpage604 includes an identifier field 606 and/or text entry field 608 (e.g.,credential/password field) associated with a set of one or morerestricted resources. For example, browser interface 600 did not detectthe login resources in the markup language, and as a result, did notautofill one or both of identifier field 606 and the text entry field608 (e.g., credential/password field). In another example, while themark-up language for a webpage designates a text field as having thePASSWORD attribute (indicating that the value is to be obscured as it isbeing entered), such fields are known to be used for purposes other thancredential entry (e.g., for entry of sensitive data such as birthdates).

As such, referring to FIG. 6B, electronic device configures browserinterface 600 to display a credential affordance 620 associated with thetext entry field 608. Accordingly, in the event that an autofillprocedure does not completely fill one or more text entry fieldsassociated with one or more sets of one or more restricted resources,and/or electronic device determines that the credential affordance 620is to be displayed for providing more precise entry and management of anidentifier and/or credential, the credential affordance 620 isdisplayed. In some embodiments, credential affordance 620 is displayedeven if the autofill procedure completely fills one or more text entryfields, so as to provide the user with a mechanism for accessingalternative content for entry in the field, as described below.

For example, electronic device configures browser interface 600 todisplay credential affordance 620 based on detecting that the webpage604 includes a text entry field 608 designated as a password field(e.g., in markup language). Specifically, electronic device configuresbrowser interface 600 to determine whether the document meets a set ofone or more credential affordance display criteria. In some embodiments,the credential affordance display criteria are based on at least thedocument including text entry field 608 designated for secure textentry. In some embodiments, text entry field 608 is text that is notdisplayed, and as such, is a condition set by markup language.

In some embodiments, the credential affordance 620 is displayed in thetext entry field 608 or the identifier field 606. In some embodiments,electronic device configures browser interface 600 to display thecredential affordance 620 within or adjacent to the text entry field608. The foregoing embodiments also apply to the display of credentialaffordance 620 in the username field 606.

Referring to FIG. 6C, a selection of credential affordance 620 promptsor otherwise triggers a display of credential-assistance user interface630. As such, browser interface 600, via credential-assistance userinterface 630, allows a user to enter and manage one or more identifiersand/or credentials associated with one or more webpages. For example,electronic device and/or browser interface 600 receives a first input610 corresponding to selection of the credential affordance 620. In someembodiments, the selection is made using a mouse pointer or a contact ona touch-screen device.

Electronic device configures browser interface 600 to displaycredential-assistance user interface 630 in response to receiving thefirst input 610. In some embodiments, the credential-assistance userinterface 630 is a pop-up window or a menu. In some embodiments, todisplay the credential-assistance user interface, electronic deviceconfigures browser interface 600 to determine whether a credential(e.g., password), associated with the webpage and/or document andassociated with an identifier (e.g., domain name or displayable username), is stored in the memory.

As such, in some embodiments, electronic device configures browserinterface 600 to display one or more identifiers such as, but notlimited to, first identifier 632 (e.g., John Doe) and second identifier634 (e.g., www.webpage.com), each of which is associated with one ormore credentials in the credential-assistance user interface 630, and inaccordance with a determination that the credential is stored in thememory. Otherwise, electronic device configures browser interface 600 toforgo displaying of the identifier in the credential-assistance userinterface 630 in accordance with a determination that the credential isnot stored in the memory. For example, in the event that at least onecredential associated with webpage is not stored in the memory,electronic device configures browser interface 600 to forgo display offirst identifier 632 and/or second identifier 634.

In some embodiments, credential-assistance user interface 630 includesone or more affordances for the retrieval, entry and/or management ofone or more identifiers (e.g., usernames) and/or credentials (e.g.,passwords). For example, credential-assistance user interface 630includes one or more identifiers of webpage 604 that are associated witha respective webpage, and more specifically, one or more credentialsstored in the memory and associated with the webpage 604. In someembodiments, the one or more identifiers include first identifier 632and second identifier 634, although any number of identifiers aredisplayed in credential-assistance user interface 630.

In some embodiments, credential-assistance user interface 630 furtherincludes other identifiers affordance 636, which, when selected, causesthe device to display one or more identifiers associated with one ormore webpages distinct from webpage 604. In some embodiments,credential-assistance user interface 630 further includes generatecredential affordance 640, which generates and displays a generatedcredential (e.g., in concealed form). In some embodiments,credential-assistance user interface 630 further includes savecredential affordance 642, which stores an entered credential in thememory.

In some embodiments, credential-assistance user interface 630 furtherincludes remove credential affordance 644, which, when selected, causesthe device to remove or delete an entered credential (e.g., andassociated identifier) from the memory. In some embodiments,credential-assistance user interface 630 further includes storedcredentials affordance 648, which prompts the display to display a listof stored credentials and associated identifiers.

Referring to FIG. 6D, electronic device configures browser interface 600to receive an input 638 corresponding to selection of the identifier(e.g., first identifier 632). Further, electronic device configuresbrowser interface 600 to retrieve the credential 628 associated with theidentifier stored in the memory and enter the credential 628 into thetext entry field 608. Electronic device configures browser interface 600to correspondingly enter the identifier (e.g., first identifier 632)associated with the credential 628 into the identifier field 606. Thatis, in response to selecting the identifier (e.g., first identifier 632)in the credential-assistance user interface 630 to enter the associatedcredential in the text entry field 608 (e.g., password field),electronic device configures browser interface 600 to autopopulate theassociated identifier (e.g., first identifier 632) in the identifierfield 606 (e.g., username field).

In some embodiments, the actual characters of the credential 628 willnot be displayed in text entry field 608. As such, a concealedrepresentation of the credential 628 is displayed in text entry field608.

Referring to FIG. 6E, electronic device configures browser interface 600to display a second webpage 622 distinct from the first webpage 604.Second webpage includes a second text entry field 614 and a secondidentifier field 612. In some embodiments, electronic device configuresbrowser interface 600 to display credential-assistance user interface630 in a user interface region that is separate from the user interfaceregion that includes the text entry field 614.

Further, once separated, credential-assistance user interface 630remains separated as the user navigates from one webpage to anotherwebpage (e.g., from webpage 604 to second webpage 622). That is, in someembodiments, credential assistance user interface 630 is persistent ifmoved after it is prompted and separated, and the contents changes orupdates automatically as the browser interface focus changes (e.g., movefrom one webpage or domain to another webpage or domain). For instance,as the browser interface 600 navigated from the webpage 604 to thesecond webpage 622, a display of the credential-assistance userinterface 630 updated to include a third identifier 646 (e.g., “JaneSmith”) associated with a credential of the second webpage 622.

In some embodiments, electronic device configures browser interface 600to receive a selection of the stored credentials affordance 648. Assuch, electronic device configures browser interface 600 to display allstored identifier affordances of one or more webpages (e.g., webpage 604and/or second webpage 622). In some embodiments, electronic deviceconfigures browser interface 600 to receive a selection of the storedcredentials affordance 648. As such, electronic device configuresbrowser interface 600 to display identifiers associated with one or morewebpages distinct from the webpage 604.

In some embodiments, the stored identifiers are displayed along withdomains to which they correspond. In some embodiments the storedidentifiers are displayed along with an indication of when the storedcredential was initially stored or when the credential was last used. Insome embodiments, in response to requesting more information about anidentifier, the device displays options to use the password associatedwith the identifier, open a link to a website associated with theidentifier, remove the identifier and corresponding credential fromstorage, and edit the credential and/or the identifier.

Referring to FIGS. 6F and 6G, an example user interface of selecting andgenerating the generate credential affordance 640 is illustrated inaccordance with some embodiments. Specifically, browser interface 600receives an input corresponding to a selection of the generatecredential affordance 640. Electronic device configures browserinterface 600 to generate and display a generated credential 650. Insome embodiments, the generated credential 650 is a secure passwordgenerated automatically without further input from the user. The userthen selects the generated credential 650 and, in response to theselection, electronic device configures browser interface 600 toassociate the generated credential 650 with an entered identifier (e.g.,username) and store the generated credential 650 in memory.

In some embodiments, as shown in FIG. 6H, electronic device configuresbrowser interface 600 to forgo display of generate credential affordance640 if text has been entered in the text entry field 608 (e.g.,credential/password field). For example, electronic device configuresbrowser interface 600 to display a plurality of password options withoutdisplaying an active option for generating a new credential based on adetermination that text has been entered in the text entry field 608. Insome embodiments, the appearance of the generate credential affordance640 is grayed-out if text has been entered in the text entry field 608.In some embodiments, the generate credential affordance 640 is disabledif text has been entered in the text entry field 608.

Referring to FIG. 6I, electronic device configures browser interface 600to save or otherwise store text entered into text entry field 608 as acredential and into the memory. In some embodiments, electronic deviceconfigures browser interface 600 to receive an input corresponding toselection of the save credential affordance 642. Further, electronicdevice configures browser interface 600 to store the entered text as acredential with or without associating the entered text with anidentifier.

For example, in some embodiments, the entered text is entered inconjunction with an identifier entered in identifier field 606. As such,the entered text (e.g., credential/password) is saved in conjunctionwith and associated with an identifier. In some embodiments, the enteredtext is entered without an identifier entered in identifier field 606.Accordingly, electronic device configures browser interface 600 to storethe entered text in the memory without an association to an identifier.

In some embodiments, a selection of the save credential affordance 642associates or links a credential (e.g., password) with an identifier(e.g., username) subsequently entered in tandem with the credential onthe same webpage. For example, electronic device configures browserinterface 600 to determine whether text entry field (e.g., identifierfield 606) associated with the text entry field 608 includes an enteredidentifier. Electronic device configures browser interface 600 toassociate the entered text (e.g., password) with the entered identifier(e.g., username) as a stored credential for the entered identifier basedon a determination that the text entry field 608 associated with thetext entry field (e.g., identifier field 606) includes the enteredidentifier. In some embodiments, the foregoing occurs before a usersubmits a credential and identifier to access the resource.

In some embodiments, an appearance of the text entry field 608 (e.g.,credential/password field) changes when a credential is saved toindicate that the credential is saved (e.g., change background fromwhite to yellow). In some embodiments, a stored credential is suggestedfor a confirm credential field during, for example, account setup.Specifically, in an account setup stage, a webpage displays a secondtext field requesting to confirm an entered password in and below afirst text field. As such, a stored credential is suggested in theconfirm credential field.

Referring to FIG. 6J, in some embodiments, browser interface 600 allowsthe user to change the credentials (e.g., password) for all similaridentifiers to the entered credential having the same identifier.Specifically, electronic device configures browser interface 600 todetermine whether an identifier entered in the identifier field 606 isthe same as an identifier stored in the memory and associated with adifferent credential than the one entered in the text entry field 608.

Browser interface 600 displays a credential update affordance 656 incredential-assistance user interface 630 in response to determining thatan entered identifier is the same as a stored identifier. In someembodiments, the credential update affordance 656 requests user confirmwhether to change all credentials associated with same identifier to theentered credential. Upon selecting “Yes”, electronic device configuresbrowser interface 600 to change all credentials of the storedidentifiers that are the same as the entered identifier to the enteredcredential. As such, in some embodiments, an association of all same orsimilar identifiers is updated from an association to a respectivecurrent credential to the entered credential. That is, the credentialfor each of the same identifiers is updated to or replaced by theentered credential.

Referring to FIG. 6K, electronic device configures browser interface 600to automatically generate and display a generated credential 650 basedon a determination that a weak credential has been entered.Specifically, for example, electronic device configures browserinterface 600 to determine whether an entered credential 662 meets acredential strength standard. Further, electronic device configuresbrowser interface 600 to generate and display a generated credential 650meeting the credential strength standard in accordance with adetermination that the entered credential does not meet the credentialstrength standard.

Referring to FIGS. 6L and 6M, the credential-assistance user interface630 includes a search stored credentials affordance 646 for searchingthrough stored credentials. For example, a selection of the searchstored credentials affordance 646 prompts a search field. Text isentered in the search field for use in searching through the memory forstored identifiers and/or credentials.

Referring to FIG. 6N, credential-assistance user interface 630 providesan option to remove or delete a credential. For example, after browserinterface 600 autofills text entry field 608 with a stored credential, auser desires to remove the credential from the text entry field anddelete it from the memory. As such, electronic device configures browserinterface 600 to remove the automatically filled credential from thetext entry field 608 and removing the automatically filled credentialfrom the memory in response to receiving the input corresponding toselection of the remove credential affordance 644.

Referring to FIG. 6O, in some embodiments, the electronic deviceconfigures browser interface 600 to receive a selection of the otheridentifiers affordance 636. In response to a selection of the otheridentifiers affordance 636, credential-assistance user interface 630displays the names of identifiers (e.g., N^(th) identifier 650) forcredentials other than the identifiers associated with webpage 604.Specifically, electronic device configures browser interface 600 toinclude a display other identifiers affordance 636 in thecredential-assistance user interface 630 that displays one or moreidentifiers associated with one or more additional sets of one or morerestricted resources.

Referring to FIG. 6P, in some embodiments, the electronic deviceconfigures browser interface 600 to display a document (e.g., webpage672) without displaying credential affordance 620 (FIG. 6B) and withoutfilling in the text entry field 670 based on a determination that thetext entry field (e.g., text entry field 670, FIG. 6P) is not acredential entry field (e.g., password field).

FIGS. 7A and 7B are flow diagrams illustrating a method of credentialentry and management using an electronic device and in accordance withsome embodiments. Methods 700 and/or 720 can optionally be performed ata device (e.g., portable multifunction devices 100, 300, and/or 500)with a display and a memory (102, 370, and 518). Some operations inmethods 700 and/or 720 can optionally be combined, the order of someoperations can optionally be changed or altered, and some operations canoptionally be omitted.

As described below, methods 700 and 720 provide an intuitive way forreadily entering and managing credentials, for example, in a browserinterface of a browser application. The method reduces the cognitiveand/or physical burden on a user during such entry and/or management,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to enter and managecredentials more efficiently conserves power and increases the timebetween battery charges.

Referring to FIG. 7A, at block 702, method 700 displays, on the display(e.g., display 112, FIG. 1), a text entry field (e.g., text entry field608, FIG. 6) associated with a set of one or more restricted resources(e.g., first webpage 604) and a credential affordance (e.g., credentialaffordance 620, FIG. 6B) associated with the text entry field. At block704, method 700 receives a first input corresponding to selection of thecredential affordance.

At blocks 706-710, method 700 can optionally, in response to receivingthe first input (e.g., first input 610, FIG. 6C), display acredential-assistance user interface (credential-assistance userinterface 630, FIG. 6C). Specifically, at block 706, method 700 canoptionally, in response to receiving the first input, determine whethera credential is stored in the memory (e.g., memory 102, FIG. 1). Atblock 708, method 700 can optionally, in accordance with a determinationthat the credential is not stored in the memory, forgo display of theidentifier (e.g., first identifier 632, FIG. 6C) in thecredential-assistance user interface.

However, at block 710, method 700 can optionally, in accordance with adetermination that a credential is stored in the memory, display anidentifier (e.g., first identifier 632, FIG. 6D) associated with thecredential (e.g., credential 628, FIG. 6D) in the credential-assistanceuser interface. At block 712, method 700 receives an input correspondingto selection of the identifier. At block 714, method 700 can optionally,in response to receiving the input (e.g., input 638, FIG. 6D)corresponding to selection of the identifier, retrieve the credentialstored in the memory and enter the credential into the text entry field.

In some embodiments, entering the credential into the text entry fieldincludes displaying a concealed representation of the credential in thetext entry field.

In some embodiments, the method further includes in response toreceiving the first input corresponding to selection of the credentialaffordance and in accordance with the determination that a secondcredential associated with a second set of one or more restrictedresources and a second identifier is stored in the memory, displaying anaccess stored identifiers affordance (e.g., other identifiers affordance636 or stored credentials affordance 648, FIG. 6C); receiving an inputcorresponding to selection of the access stored identifiers affordance;and in response to receiving the input corresponding to selection of theaccess stored identifiers affordance, displaying, in thecredential-assistance user interface, a plurality of stored identifiersincluding the identifier and the second identifier.

In some embodiments, the credential-assistance user interface isdisplayed in a user interface region that is separate from the userinterface region that includes the text entry field.

In some embodiments, the credential-assistance user interface 630 (FIG.6C) is displayed in a first position (e.g., displayed below the textentry field 608 in FIG. 6C), the method further includes whiledisplaying the credential-assistance user interface 630 (FIG. 6C) in thefirst position, receiving an input corresponding to a request to displaythe credential-assistance user interface in a second position (e.g.,displayed partially outside the browser interface 600 in FIG. 6E); andin response to receiving the input corresponding to the request todisplay the credential-assistance user interface 630 (FIG. 6E) in thesecond position, displaying the credential-assistance user interface inthe second position, wherein the second position is distinct from thefirst position and separate from the user interface region that includesthe text entry field (e.g., text entry field 608 of FIG. 6C, or textentry field 614 of FIG. 6E).

In some embodiments, the method further includes while displaying thecredential-assistance user interface (e.g., credential-assistance userinterface 630, FIG. 6E) in the second position, receiving an inputcorresponding to a request to display a second text entry field (e.g.,second text entry field 614 on a different webpage, FIG. 6E); inresponse to receiving the input corresponding to a request to display asecond text entry field: displaying the second text entry field, whereinthe second text entry field is distinct from the text entry field andwherein the second text entry field is associated with a third set ofone or more restricted resources; and replacing, in thecredential-assistance user interface, display of the identifierassociated with the credential with display of a distinct identifier(e.g., third identifier 646—“Jane Smith”) associated with a distinctcredential, wherein the distinct credential is associated with the thirdset of one or more restricted resources.

In some embodiments, the method further includes in response toreceiving the first input (e.g., first input 610, FIG. 6C) correspondingto selection of the credential affordance (e.g., credential affordance620, FIG. 6C), determining whether text has been entered in the textentry field; in accordance with a determination that text has not beenentered in the text entry field, displaying a generate-credentialaffordance (e.g., generate-credential affordance 640); receiving aninput corresponding to selection of the generate-credential affordance;and in response to receiving the input corresponding to selection of thegenerate-credential affordance, generating and displaying a generatedcredential (e.g., generated credential 650).

In some embodiments, the method further includes, in accordance with adetermination that text has been entered in the text entry field,displaying a plurality of password options without displaying an activeoption for generating a new credential.

In some embodiments, the method further includes, receiving an inputcorresponding to selection of the generated credential; and in responseto receiving the input corresponding to selection of the generatedcredential, associating the generated credential with a third identifierand storing the generated credential in the memory.

In some embodiments, the method further includes, in response toreceiving the first input corresponding to selection of the credentialaffordance and in accordance with a determination that the text entryfield includes entered text, displaying a save credential affordance(e.g., save credential affordance 642, FIG. 6C).

In some embodiments, the method further includes, receiving an input(e.g., input 616, FIG. 6I) corresponding to selection of the savecredential affordance; and in response to receiving the inputcorresponding to selection of the save credential affordance, storingthe entered text as a credential without associating the entered textwith a fourth identifier.

In some embodiments, the method further includes receiving an input(e.g., input 616, FIG. 6I) corresponding to selection of the savecredential affordance (e.g., save credential affordance 642, FIG. 6I);and in response to receiving the input corresponding to selection of thesave credential affordance, associating the entered text (e.g.,credential/password entered in text entry field 608, FIG. 6I) with afourth identifier (e.g., entered in identifier field 606, FIG. 6I) andstoring the entered text as a credential for the fourth identifier.

In some embodiments, the method further includes receiving an input(e.g., input 616, FIG. 6I) corresponding to selection of the savecredential affordance (e.g., save credential affordance 642, FIG. 6I);in response to receiving the input corresponding to selection of thesave credential affordance, determining whether a third text entry field(e.g., identifier field 606, FIG. 6I) associated with the text entryfield 608 (FIG. 6I) includes an entered identifier (e.g., username); andin accordance with a determination that the third text entry fieldassociated with the text entry field includes the entered identifier,associating the entered text with the entered identifier as a storedcredential for the entered identifier.

In some embodiments, the method further includes receiving an input(e.g., input 616, FIG. 6I) corresponding to selection of the savecredential affordance (e.g., save credential affordance 642, FIG. 6I);in response to receiving the input corresponding to selection of thesave credential affordance, determining whether a fourth identifier(e.g., first username) entered in a third text entry field (e.g.,identifier field 606, FIG. 6I) associated with the text entry field isthe same as a fifth identifier (e.g. second username) stored in thememory associated with a third credential (e.g., credential/password),wherein a third credential is distinct from an entered credential; inaccordance with a determination that the fourth identifier entered in athird text entry field associated with the text entry field is the sameas the fifth identifier stored in the memory, displaying a credentialupdate affordance (e.g., credential update affordance 656, FIG. 6J); inaccordance with a determination that the fourth identifier entered in athird text entry field associated with the text entry field is not thesame as the fifth identifier stored in the memory, forgoing display ofthe credential update affordance and storing the fourth identifier andthe entered credential in the memory; and while displaying thecredential update affordance: receiving an input corresponding toselection of the credential update affordance (e.g., selecting “Yes”affordance, FIG. 6J); and in response to receiving the inputcorresponding to selection of the credential update affordance, updatingthe association of the fifth identifier from the third credential to theentered credential.

In some embodiments, the method further includes receiving an input(e.g., input 616, FIG. 6I) corresponding to selection of the savecredential affordance (e.g., save credential affordance 642, FIG. 6I);in response to receiving the input corresponding to selection of thesave credential affordance, determining whether an entered credential(e.g., credential 662 entered in text entry field 608, FIG. 6K) meets acredential strength standard, wherein the credential strength standardincludes one or more rules associated with formation of credentials; inaccordance with a determination that the entered credential does notmeet the credential strength standard, generating and displaying agenerated credential (e.g., generated credential 650, FIG. 6K) meetingthe credential strength standard; and in accordance a determination thatthe entered credential meets the credential strength standard,associating the entered credential with a fourth identifier (e.g.,identifier entered in identifier field 606, FIG. 6K) and storing theentered credential in the memory.

In some embodiments, the method further includes receiving an input(e.g., input 616, FIG. 6I) corresponding to selection of the savecredential affordance (e.g., save credential affordance 642, FIG. 6I);in response to receiving the input corresponding to selection of thesave credential affordance, adjusting the text entry field (e.g., textentry field 608, FIG. 6I) from a first appearance (e.g., first color) toa second appearance (e.g., second color) different from the firstappearance.

In some embodiments, the method further includes displaying a fourthtext entry field (e.g., text entry field 608, FIG. 6I) associated withthe first text entry field; in response to receiving the inputcorresponding to selection of the second identifier (e.g., firstidentifier 632, FIG. 6I), displaying a saved credential (e.g.,credential/password in concealed form, FIG. 6I) in the fourth text entryfield.

In some embodiments, the method further includes, thecredential-assistance user interface (e.g., credential-assistance userinterface 630, FIG. 6C) includes a display additional identifieraffordance (e.g., other identifiers affordance 636 or stored credentialsaffordance 648, FIG. 6C) that displays one or more identifiers (e.g.,usernames) associated with one or more additional sets of one or morerestricted resources (e.g., webpages), wherein the one or moreadditional sets of one or more restricted resources are distinct fromthe set of one or more restricted resources.

In some embodiments, the method further includes thecredential-assistance user interface includes a search entry field(e.g., search field, FIG. 6M) for searching one or more storedcredentials.

In some embodiments in which displaying the text entry field includesdisplaying the text entry field having an automatically filledcredential stored in the memory, and wherein the credential-assistanceuser interface includes a remove credential affordance, the methodfurther includes receiving an input corresponding to selection of theremove credential affordance (e.g., remove credential affordance 644,FIG. 6N); and in response to receiving the input corresponding toselection of the remove credential affordance, removing theautomatically filled credential from the text entry field and removingthe automatically filled credential from the memory.

In some embodiments in which displaying the credential affordanceassociated with the text entry field includes displaying the credentialaffordance within or adjacent to the text entry field.

In some embodiments, the text entry field is one of a username field ora password field.

In some embodiments, the set of one or more restricted resources is awebpage, and wherein the identifier is a domain of the webpage.

In some embodiments, the identifier is a username.

In some embodiments, the credential is a password.

Referring to FIG. 7B, at block 702, method 720 receives a request todisplay a document (e.g., webpage 604, FIG. 6A) that includes a textentry field (e.g., text entry field 608 (FIG. 6A). At block 724 to 728,method 720 can optionally, in response to receiving the request, displaythe document with the text entry field. Specifically, at block 724,method 720 can optionally, in response to receiving the request,determine whether the text entry field corresponds to a credential entryfield for which a stored password is available.

At block 726, method 720 can optionally, in accordance with adetermination that the text entry field corresponds to a credentialentry field for which a stored credential is available, filling in thetext entry field with the stored credential; and in accordance with adetermination that the text entry field corresponds to a credentialentry field for which a stored credential is not available, displaying,on the display, a credential affordance (e.g., credential affordance620, FIG. 6B) associated with the text entry field without filling inthe text entry field.

In some embodiments, the method further includes, in accordance with adetermination that the text entry field (e.g., text entry field 670,FIG. 6P) is not a credential entry field (e.g., password field),displaying the document (e.g., webpage) without displaying thecredential affordance (e.g., credential affordance 620, FIG. 6B) andwithout filling in the text entry field.

In some embodiments, determining whether text entry field is acredential entry field is based on markup language associated with thetext entry field.

In some embodiments, the method further includes receiving a secondinput corresponding to selection of the credential affordance; inresponse to receiving the second input, displaying acredential-assistance user interface (e.g., credential-assistance userinterface 630, FIG. 6C), wherein the credential-assistance includes oneor more of: an identifier associated with a stored credential; and anoption to generate a new password.

In accordance with some embodiments, FIG. 8 shows an exemplaryfunctional block diagram of an electronic device 800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 800 are configured to perform the techniques described above. Thefunctional blocks of the device 800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 8 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 8, an electronic device 800 includes a display unit802, a memory unit 804, and a processing unit 806 coupled to the displayunit 802 and the memory unit 804. In some embodiments, the processingunit 806 includes a receiving unit 808, retrieving unit 808, replacingunit 812, generating unit 814, associating unit 816, storing unit 818,determining unit 820, updating unit 822, adjusting unit 824, andremoving unit 826.

The processing unit 806 is configured to: display (e.g., using displayunit 802), a text entry field associated with a set of one or morerestricted resources and a credential affordance associated with thetext entry field; receive (e.g., using receiving unit 808) a first inputcorresponding to selection of the credential affordance; in response toreceiving the first input, display (e.g., using display unit 802) acredential-assistance user interface, wherein to display thecredential-assistance user interface, the processing unit 806 isconfigured to: in accordance with a determination that a credential isstored in the memory, display (e.g., using display unit 802) anidentifier associated with the credential in the credential-assistanceuser interface; and receive an input corresponding to selection of theidentifier; and in response to receiving the input corresponding toselection of the identifier, retrieve (e.g., using retrieving unit 810)the credential stored in the memory unit 804 and entering the credentialinto the text entry field.

In some embodiments, the processing unit 806 is further configured to,in accordance with a determination that the credential is not stored inthe memory unit 804, forgo display of the identifier in thecredential-assistance user interface.

In some embodiments, to enter the credential into the text entry field,the processing unit is further configured to display (e.g., usingdisplay unit 802) a concealed representation of the credential in thetext entry field.

In some embodiments, the processing unit 806 is further configured to:in response to receiving the first input corresponding to selection ofthe credential affordance and in accordance with the determination thata second credential associated with a second set of one or morerestricted resources and a second identifier is stored in the memory,display (e.g., using display unit 802) an access stored identifiersaffordance; receive (e.g., using receiving unit 808) an inputcorresponding to selection of the access stored identifiers affordance;and in response to receiving the input corresponding to selection of theaccess stored identifiers affordance, display (e.g., using display unit802), in the credential-assistance user interface, a plurality of storedidentifiers including the identifier and the second identifier.

In some embodiments, the credential-assistance user interface isdisplayed in a user interface region that is separate from the userinterface region that includes the text entry field.

In some embodiments, the credential-assistance user interface isdisplayed in a first position, wherein the processing unit 806 isfurther configured to: while displaying the credential-assistance userinterface in the first position, receive (e.g., using receiving unit808) an input corresponding to a request to display thecredential-assistance user interface in a second position; and inresponse to receiving the input corresponding to the request to displaythe credential-assistance user interface in the second position, display(e.g., using display unit 802) the credential-assistance user interfacein the second position, wherein the second position is distinct from thefirst position and separate from the user interface region that includesthe text entry field.

In some embodiments, the processing unit 806 is further configured to:while displaying the credential-assistance user interface in the secondposition, receive (e.g., using receiving unit 808) an inputcorresponding to a request to display a second text entry field; inresponse to receiving the input corresponding to a request to display asecond text entry field: display (e.g., using display unit 802) thesecond text entry field, wherein the second text entry field is distinctfrom the second text entry field and wherein the text entry field isassociated with a third set of one or more restricted resources; andreplace (e.g., using replacing unit 812), in the credential-assistanceuser interface, display of the identifier associated with the credentialwith display of a distinct identifier associated with a distinctcredential, wherein the distinct credential is associated with the thirdset of one or more restricted resources.

In some embodiments, the processing unit 806 is further configured to:in response to receiving the first input corresponding to selection ofthe credential affordance, determine (e.g., using determining unit 820)whether text has been entered in the text entry field; in accordancewith a determination that text has not been entered in the text entryfield, display (e.g., using display unit 802) a generate-credentialaffordance; receive (e.g., receiving unit 808) an input corresponding toselection of the generate-credential affordance; and in response toreceiving the input corresponding to selection of thegenerate-credential affordance, generate (e.g., using generating unit814) and display (e.g., using display unit 802) a generated credential.

In some embodiments, the processing unit 806 is further configured to,in accordance with a determination that text has been entered in thetext entry field, display (e.g., using display unit 802) a plurality ofpassword options without displaying an active option for generating anew credential.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the generated credential; and in response to receiving theinput corresponding to selection of the generated credential, associate(e.g., using associating unit 816) the generated credential with a thirdidentifier and storing the generated credential in the memory.

In some embodiments, the processing unit 806 is further configured to:in response to receiving the first input corresponding to selection ofthe credential affordance and in accordance with a determination thatthe text entry field includes entered text, display (e.g., using displayunit 802) a save credential affordance.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the save credential affordance; and in response toreceiving the input corresponding to selection of the save credentialaffordance, store (e.g., using storing unit 818) the entered text as acredential without associating the entered text with a fourthidentifier.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the save credential affordance; and in response toreceiving the input corresponding to selection of the save credentialaffordance, associate (e.g., using associating unit 816) the enteredtext with a fourth identifier and storing the entered text as acredential for the fourth identifier.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the save credential affordance; in response to receivingthe input corresponding to selection of the save credential affordance,determine (e.g., using determining unit 820) whether a third text entryfield associated with the text entry field includes an enteredidentifier; and in accordance with a determination that the third textentry field associated with the text entry field includes the enteredidentifier, associate (e.g., using associating unit 816) the enteredtext with the entered identifier as a stored credential for the enteredidentifier.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the save credential affordance; in response to receivingthe input corresponding to selection of the save credential affordance,determine (e.g., using determining unit 820) whether a fourth identifierentered in a third text entry field associated with the text entry fieldis the same as a fifth identifier stored in the memory associated with athird credential, wherein a third credential is distinct from an enteredcredential; in accordance with a determination that the fourthidentifier entered in a third text entry field associated with the textentry field is the same as the fifth identifier stored in the memory,display (e.g., using display unit 802) a credential update affordance;in accordance with a determination that the fourth identifier entered ina third text entry field associated with the text entry field is not thesame as the fifth identifier stored in the memory, forgo display of thecredential update affordance and storing the fourth identifier and theentered credential in the memory; and while displaying the credentialupdate affordance: receive (e.g., using receiving unit 808) an inputcorresponding to selection of the credential update affordance; and inresponse to receiving the input corresponding to selection of thecredential update affordance, update (e.g., using updating unit 822) theassociation of the fifth identifier from the third credential to theentered credential.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the save credential affordance; in response to receivingthe input corresponding to selection of the save credential affordance,determine (e.g., using determining unit 820) whether an enteredcredential meets a credential strength standard, wherein the credentialstrength standard includes one or more rules associated with formationof credentials; in accordance with a determination that the enteredcredential does not meet the credential strength standard, generate(e.g., using generating unit 814) and display (e.g., using display unit802) a generated credential meeting the credential strength standard;and in accordance a determination that the entered credential meets thecredential strength standard, associate (e.g., using associating unit824) the entered credential with a fourth identifier and storing theentered credential in the memory.

In some embodiments, the processing unit 806 is further configured to:receive (e.g., using receiving unit 808) an input corresponding toselection of the save credential affordance; in response to receivingthe input corresponding to selection of the save credential affordance,adjust (e.g., using adjusting unit 824) the text entry field from afirst appearance to a second appearance different from the firstappearance.

In some embodiments, the processing unit 806 is further configured to:display (e.g., using display unit 802) a fourth text entry fieldassociated with the first text entry field; in response to receiving theinput corresponding to selection of the second identifier, display(e.g., using display unit 802) a saved credential in the fourth textentry field.

In some embodiments, the credential-assistance user interface includes adisplay additional identifier affordance that displays one or moreidentifiers associated with one or more additional sets of one or morerestricted resources, wherein the one or more additional sets of one ormore restricted resources are distinct from the set of one or morerestricted resources.

In some embodiments, the credential-assistance user interface includes asearch entry field for searching one or more stored credentials.

In some embodiments, to display the text entry field, the processingunit 806 is further configured to display (e.g., using display unit 802)the text entry field having an automatically filled credential stored inthe memory, and wherein the credential-assistance user interfaceincludes a remove credential affordance, the processing unit 806 isfurther configured to: receive (e.g., using receiving unit 808) an inputcorresponding to selection of the remove credential affordance; and inresponse to receiving the input corresponding to selection of the removecredential affordance, remove (e.g., using removing unit 826) theautomatically filled credential from the text entry field and removingthe automatically filled credential from the memory.

In some embodiments, to display the credential affordance associatedwith the text entry field, the processing unit 806 is further configuredto display the credential affordance within or adjacent to the textentry field.

In some embodiments, the text entry field is one of a username field ora password field.

In some embodiments, the set of one or more restricted resources is awebpage, and wherein the identifier is a domain of the webpage.

In some embodiments, the identifier is a username.

In some embodiments, the credential is a password.

The operations described above with reference to FIG. 7A are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 8.For example, displaying operation 702, receiving operation 704,determining operation 706, forgoing operation 708, displaying operation710, receiving operation 712, retrieving operation 714, can optionallybe implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 canoptionally utilize or call data updater 176 or object updater 177 toupdate the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 9 shows an exemplaryfunctional block diagram of an electronic device 900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 900 are configured to perform the techniques described above. Thefunctional blocks of the device 900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 9 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 9, an electronic device 900 includes a display unit902, an audio output unit 904, and a processing unit 906 coupled to thedisplay unit 902 and the memory unit 904. In some embodiments, theprocessing unit 906 includes a receiving unit 808 and a filling unit810.

The processing unit 906 is configured to: receive (e.g., using receivingunit 808) a request to display, on the display unit 902, a document thatincludes a text entry field; in response to receiving the request,display, on the display unit 902, the document with the text entryfield, wherein to display the document with the text entry field, theprocessing unit is configured to: in accordance with a determinationthat the text entry field corresponds to a credential entry field forwhich a stored credential is available, fill (e.g., using filling unit910) in the text entry field with the stored credential; and inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is not available,display, on the display unit 902, a credential affordance associatedwith the text entry field without filling in the text entry field.

In some embodiments, the processing unit 906 is configured to, inaccordance with a determination that the text entry field is not acredential entry field, displaying (e.g., using display unit 902) thedocument without displaying credential affordance and without filling inthe text entry field.

In some embodiments, determining whether text entry field is acredential entry field is based on markup language associated with thetext entry field.

In some embodiments, the processing unit 906 is configured to: receive(e.g., using receiving unit 908) a second input corresponding toselection of the credential affordance; in response to receiving thesecond input, display a credential-assistance user interface, whereinthe credential-assistance includes one or more of: an identifierassociated with a stored credential; and an option to generate a newpassword.

The operations described above with reference to FIG. 7B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 9.For example, displaying operation 722, determining operation 724,filling operation 726, and displaying operation 728, can optionally beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 canoptionally utilize or call data updater 176 or object updater 177 toupdate the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. An electronic device comprising: one or moreprocessors; memory; a display; and one or more programs stored inmemory, the one or more programs including instructions for: receiving arequest to display a document that includes a text entry field; inresponse to receiving the request, displaying the document with the textentry field, wherein displaying the document with the text entry fieldincludes: in accordance with a determination that the text entry fieldcorresponds to a credential entry field for which a stored credential isavailable, displaying a credential-assistance user interface associatedwith at least the stored credential; and in accordance with adetermination that the text entry field corresponds to a credentialentry field for which a stored credential is not available, displaying,on the display, a credential affordance associated with the text entryfield without filling in the text entry field.
 2. The electronic deviceof claim 1, the one or more programs further including instructions for:in accordance with a determination that the text entry field is not acredential entry field, displaying the document without displaying thecredential-assistance user interface and without displaying thecredential affordance.
 3. The electronic device of claim 1, whereindetermining whether the text entry field is a credential entry field isbased on markup language associated with the text entry field.
 4. Theelectronic device of claim 1, the one or more programs further includinginstructions for: receiving a second input corresponding to selection ofthe credential affordance; and in response to receiving the secondinput, displaying a credential-assistance user interface, wherein thecredential-assistance user interface includes one or more of: anidentifier associated with a stored credential; and an option togenerate a new password.
 5. A method comprising: at an electronic deviceincluding a display and memory: receiving a request to display adocument that includes a text entry field; in response to receiving therequest, displaying the document with the text entry field, whereindisplaying the document with the text entry field includes: inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is available,displaying a credential-assistance user interface associated with atleast the stored credential; and in accordance with a determination thatthe text entry field corresponds to a credential entry field for which astored credential is not available, displaying, on the display, acredential affordance associated with the text entry field withoutfilling in the text entry field.
 6. The method of claim 5, furthercomprising, in accordance with a determination that the text entry fieldis not a credential entry field, displaying the document withoutdisplaying the credential-assistance user interface and withoutdisplaying the credential affordance.
 7. The method of claim 5, whereindetermining whether the text entry field is a credential entry field isbased on markup language associated with the text entry field.
 8. Themethod of claim 5, further comprising: receiving a second inputcorresponding to selection of the credential affordance; and in responseto receiving the second input, displaying a credential-assistance userinterface, wherein the credential-assistance user interface includes oneor more of: an identifier associated with a stored credential; and anoption to generate a new password.
 9. A non-transitory computer-readablestorage medium comprising one or more programs for execution by one ormore processors of an electronic device with a display, the one or moreprograms including instructions which, when executed by the one or moreprocessors, cause the electronic device to: receive a request to displaya document that includes a text entry field; in response to receivingthe request, display the document with the text entry field, whereindisplaying the document with the text entry field includes: inaccordance with a determination that the text entry field corresponds toa credential entry field for which a stored credential is available, displaying a credential-assistance user interface associated with at leastthe stored credential; and in accordance with a determination that thetext entry field corresponds to a credential entry field for which astored credential is not available, display a credential affordanceassociated with the text entry field without filling in the text entryfield.
 10. The non-transitory computer-readable storage medium of claim9, wherein the one or more programs further include instructions which,when executed by the one or more processors, cause the electronic deviceto: in accordance with a determination that the text entry field is nota credential entry field, display the document without displaying thecredential-assistance user interface and without displaying thecredential affordance.
 11. The non-transitory computer-readable storagemedium of claim 9, wherein determining whether the text entry field is acredential entry field is based on markup language associated with thetext entry field.
 12. The non-transitory computer-readable storagemedium of claim 9, wherein the one or more programs further includeinstructions which, when executed by the one or more processors, causethe electronic device to: receive a second input corresponding toselection of the credential affordance; and in response to receiving thesecond input, display a credential-assistance user interface, whereinthe credential-assistance user interface includes one or more of: anidentifier associated with a stored credential; and an option togenerate a new password.